Production planning and monitoring in inkjet devices

ABSTRACT

An inkjet printer is placed in communications with a print production planning and scheduling system to allow planning, monitoring, and adjusting of an automatic digital (ink jet) printing production line. In one embodiment, the order of the print jobs is defined by the print shop owner or by the associated supervisor. Each job becomes a paper based (printed) job ticket and the order in which the jobs arrive at the print operator side defines the print order. The same is true for the order at the RIP side. Any change in regards to this order requires a direct communication of the print shop owner or supervisor with the printer or RIP operator.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. provisional patent applicationSer. No. 61/706,040, filed Sep. 26, 2012, which application isincorporated herein in its entirety by this reference thereto.

BACKGROUND OF THE INVENTION

1. Technical Field

The invention relates to printing. More particularly, the inventionrelates to production planning and monitoring in digital inkjet printingsystems.

2. Description of the Background Art

The digital printing process is becoming more and more automated. Allsteps from the ordering until the delivery of the print product arelinked together and monitored by an MIS system. Apart from this, it isnecessary to handle the customer requests as carefully as possible toavoid mistakes and additional production runs to be able to deliver theproduct in the requested quality on time. This requires that allinvolved subsystems stay connected and get the correct job relatedinformation together with the job without the need for additional userinteractions.

Production planning and scheduling systems, such as EFI's PrintFlowproduct (Electronics For Imaging, Inc., Foster City, Calif.), are widelyused in the analog and toner based printing world. These systemsoptimize the production process and thus avoid waste and delays becauseof their capabilities for planning demand, monitoring status, andreacting to changes from the requirement side (new incoming orders,priority changes) or from the production (device) side.

In the wide format, super wide format or, more generally, in the ink jetworld this kind of technology is not usable because known printingdevices do not have the capability to communicate actively currentdevice and job status, display the job order in the way it was scheduledfrom a planning and scheduling system, and react in the requested way ifthe order of the print jobs changes. Furthermore, current RIP engineswhich are implemented between production planning and scheduling systemsand the inkjet printer do not have the capability to react in responseto a demand from the scheduler to move printing jobs from one device toanother.

The above described situation makes it very difficult to monitor thestatus of production in real time. It is not possible to see remotely ifand which job a printer is printing, or if the printer is in printpreparation, in maintenance mode, out of order, etc. Furthermore, anyshort time adjustments in the print order are very time consuming andrequire direct interaction. This is especially true in the case where aprinter is out of order for a while and, as a result, the dailyproduction must be rearranged, which requires a significant amount ofdirect communication and monitoring from the print shop owner orsupervisor.

Further, changing the media on a roll printer is time consuming and acertain amount of extra media is typically required to wind and tack themedia at the winding roll. The same is true if a printer has to beswitched from one ink set to another. Also, this requires some time forprint preparation and typically also includes an extra purge or otheradditional filling steps which affect the ink consumption.

Status updates have the same problem. Either there is a manual procedurewhich requests that the printer operator enter the status of aparticular print job, at least issue a signal that it is printed, orthere is only the option to request the job status in verbal or writtenform. A request to move urgent jobs from one inkjet printer which isheavily used or in maintenance for the moment to another available inkjet printing system requires a similar, time consuming, and error pronecommunication effort between all involved persons, i.e. administrator orsupervisor, RIP operator, and printer operator.

Further, a typical digital print shop uses a paper based job ticket foreach and every job to produce its print product. This job ticket is adocument that includes high level parameters, such as the name andaddress of the customer, the name of the content file, the requestedmedia, and certain job related definitions, such as the output size orthe number of copies. The specific production parameters which are setat the digital printing press are affected by the skill set of theprinting press operator. Thus, the quality and/or color of the resultingprint product, is very much related to the settings that the printingpress operator makes to the printing press.

All of these limitations make an optimization of the print productionrelated to specific parameters or rules impossible.

SUMMARY OF THE INVENTION

Embodiments of the invention provide a technique that allows an inkjetprinter to be connected to a print production planning and schedulingsystem. Embodiments of the invention also provide a combination of aproduction planning and scheduling system and a wide format or superwide format ink jet system where communication between these two unitsis established. Embodiments of the invention also allow a RIP unit tobecome a hub between the planning and scheduling system and the printer.Thus, embodiments of the invention overcome the above limitations andoffer a solution for planning, monitoring, and adjusting an automaticdigital (ink jet) printing production line.

In one embodiment, the order of the print jobs is defined by the printshop owner or by the associated supervisor. Each job becomes a paperbased (printed) job ticket and the order in which the jobs arrive at theprint operator side defines the print order. The same is true for theorder at the RIP side. Any change in regards to this order requires adirect communication of the print shop owner or supervisor with theprinter or RIP operator.

Another embodiment of the invention allows the operator at the time oforder entry to define the complete production run, including printingpress parameters which are today only in the hand of the printeroperator. The job is created and associated to the selected, specificprinting press and available printing options for such specific printingpress. All parameters which are needed to print this job as defined arestored within the associated digital job ticket. This avoids, forexample, mistakes within the needed further production steps, expensivereproduction or correction post a first print run, and different outputresults if the production runs on different machines or different sides.

This aspect of the invention thus achieves a consistent and constantoutput quality of print production because it moves the responsibilityof the printer operator into an automated and monitored process which anadministrator or a skilled person can configure prior to the real printproduction. The output quality thus becomes less dependent on theprinter operator's skill set. If a customer requests an additionalamount of previously printed product (reproduction), then this techniquemakes it possible to create a job using exactly the same printingparameters. As such, achieving the same output quality as the previouslydelivered print production becomes predictable and simpler.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block schematic diagram that shows an architecture forproduction planning and monitoring of inkjet devices according to theinvention;

FIG. 2 is a high level block schematic diagram of JDF integrationbetween the DSF and a printer according to the invention;

FIG. 3 is a block schematic diagram that shows RIP to printerintegration and depicts how the RIP communicates with the printer, aswell as which parts of the printer are linked and the manner in whichthey are linked, according to the invention;

FIG. 4 shows a mapping tool for media according to the invention;

FIG. 5 is a block schematic diagram that shows a system architecturethat supports a dashboard and notification services according to theinvention;

FIG. 6 is a screen shot showing a dialog for printer setup in a RIPaccording to the invention;

FIG. 7 is a screen shot showing a first step in dashboard registration,agent installation and notifications setup according to the invention;

FIG. 8 is a screen shot showing notifications setup where a dashboardlicense has already been purchased and installed according to theinvention;

FIG. 9 is a block schematic diagram showing a dashboard andnotifications workflow according to the invention;

FIGS. 10-14 show a dashboard user interface according to the invention;and

FIG. 15 is a block schematic diagram that depicts a machine in theexemplary form of a computer system within which a set of instructionsfor causing the machine to perform any of the herein disclosedmethodologies may be executed.

DETAILED DESCRIPTION OF THE INVENTION Definitions and Acronyms

For purposes of the discussion herein, the following terms and acronymshave the attributed meaning:

UI—User Interface, an application used for job submission, jobmanagement, and for controlling printers;

Printer—the printer refers to the print engine itself, as well as to thesuite of middleware print services and the UI running on a dedicatedLinux or other system that is attached to the print engine;

CORBA—Common Object Request Broker Architecture;

JDF—Job Definition Format;

JMF—Job Messaging Format;

RIP—Raster Image Processor, such as EFI's Fiery XF RIP;

MIS—Management Information System, such as EFI's Pace and Monarch MIS;and

DSF—Digital Store Front.

Discussion

Today digital inkjet presses have a lot of specific parameters which theprinter operator sets depending on the operator's knowledge, experience,and the particular job requirements. This opens the door for expensivemistakes during particular print production runs. The herein describedtechnique make it possible for the digital inkjet printing press tocommunicate details of available parameters while connecting within theprint architecture, such that the systems which are creating anddefining the print jobs, e.g. RIP, MIS, store front, are using theparameters as announced.

Embodiments of the invention provide a technique that allows an inkjetprinter to be connected to a print production planning and schedulingsystem. Embodiments of the invention also provide a combination of aproduction planning and scheduling system and a wide format or superwide format ink jet system where communication between these two unitsis established. Embodiments of the invention also allow a RIP unit tobecome a hub between the planning and scheduling system and the printer.Thus, embodiments of the invention overcome the above limitations andoffer a solution for planning, monitoring, and adjusting an automaticdigital (ink jet) printing production line.

Embodiments of the invention comprise two elements, i.e.:

-   -   A facility that communicates printer specific parameters from        the digital inkjet printing press to the associated RIP unit or        connected print MIS or digital store front units; and    -   A facility that understands and uses the submitted information        for digital print production planning and job submission.

This makes it possible to plan and optimize the entire printing process.As a very simple example, embodiments of the invention avoid the need tosubmit a job which requires a white backing, i.e. creating an extrawhite layer, to a press which is not equipped with a white ink channel.Furthermore, it is also possible for particular combinations of machinesand printing parameters to be used or avoided. For instance, embodimentsof the invention allow one to request different settings where a printjob requires specified LED curing in combination with specific media, aparticular curing setting, and a particular shutter mode, while allowingregular UV ink curing on the same material.

The provision of multiple combinations of parameters is an importantaspect of the invention. In this way, the full combination of printingparameters is taken into account to allow for consistent production andoutput quality. Further, defining the print product completely at thepoint where the job enters the workflow eliminates the relationship ofthe output quality from the skill set of the available printer operator.Knowing the production parameters at the beginning allows optimizationof the whole production workflow and planning process. Thus, jobs whichrequire the same machine configuration can be queued up in such a way toreduce the amount of time for changing the machine configuration, e.g.from roll to sheet or from 4 to 8 color print mode, etc.

Interoperation of the various systems elements is as follows in anembodiment of the invention:

-   -   When the digital inkjet printing press is connected to the RIP        unit, with further connections to the print MIS or store front        systems, the press sends a message to these systems and        announces the features and options that it has available. If        there are multiple configurations of one digital printing system        on the market or one digital printing system has multiple        configuration or options possible, the RIP unit and the        connected print MIS or store front systems can then adapt their        user interface related to the published feature set so that a        user can choose from among the options which are available at        the particular digital press.    -   The selected options are sent to the digital printing press with        the job as job parameters. This step excludes the possibility        that various mistakes can be made. Thus, because of the        previously announced printing parameters, only those printing        options that are available at the printer are sent to the        printer. In such case, the printer's limitations are known in        advance, and it is therefore not possible to make requests for        unsupported options.

Embodiments of the invention also allow an operator to change processingparameters after the creation and submission of the job. For example,assume that an order for 100 banners is placed by a customer. The job isthen processed and is at the printer. At this point, the customerchanges the order and requests 120 banners. With the invention herein,it is simple to update the job from the MIS or from the store front andaccordingly update the job at the printer to have 120 banners printedinstead of only 100 banners as originally requested.

Some changes might require re-processing of the job. For example, if thecustomer has decided to use another media, then the MIS sends anAbortQueueEntry and a RemoveQueueEntry message which stops the job fromfurther processing (although the physical printing process itself is notstopped), removes the job from the RIP or the printer queue, and submitsthe updated job into the process.

FIG. 1 is a block schematic diagram that shows an architecture forproduction planning and monitoring of inkjet devices according to theinvention. In FIG. 1, a presently preferred embodiment of the inventionis shown comprising an acquisition function (DSF) (100), a managementfunction (MIS) (102), preparation function (RIP) (104), and a productionfunction (printer) (106).

The acquisition function includes a digital store front facility 10 thatprovides the management function, for example via customized customerdesktops, with requests for quotes (RFQ), specifications (SPECS), files,and payment and reorder information and that receives from themanagement function catalog information, pricing, status, and invoices;and also includes a remote access facility 11 that allows system accessand customer relations management functions.

In addition to its interaction with the acquisition function, themanagement function addressed global print business management andprovides MIS facilities that allow for job and system management 12,planning 14, reporting 16, and scheduling 18. The management functionprovides schedule and job information, specifications, and files to thepreparation function and receives status and cost information from thepreparation function.

The preparation function, as part of its interaction with the managementfunction, includes RIPs that provide, for example, proofing and photowork (20 a) and advanced PDF workflow, automated preflight, RIP, andcolor management functions (20 b). The preparation function provides jobtickets 21 (discussed in detail below) for use in connection with theproduction function. Thus, the preparation function provides scheduleand job information, specifications, and files to the productionfunction and receives status and cost information therefrom.

The production function, in addition to the printer interface function,includes printers 22, 24, 26, such as digital display graphic printersand digital page printers. These can be any type of printer, such asflatbed and hybrid wide format printers, high definitions super wideprinters, industrial inkjet systems, ceramic and other substrateprinters, as well as global support for all other printing and finishingprocesses.

Embodiments of the invention also allow the system administrator todefine and identify full media parameter configurations. Currently, suchconfigurations are related to the skill set of the printing pressoperator. Using such configurations pursuant to the invention avoidssituations where the print shop runs into quality issues and thusenables production having constant and predictable quality.

A further advantage of the herein disclosed invention is that the printshop owner can associate a particular price to a particular printoption, product, or product quality. For instance, if a digital printingpress offers two resolutions but they differ in the required printingtimes, the print shop owner can configure the pricing schema of thedigital store front in such a way that two different prices are providedand are related to the particular selected output quality. This is alsotrue for more sophisticated settings, such as omitting curing orsmoothing. Thus, jobs with specific settings are only sent to printerswhich support a particular feature, assuming the print shop has multipledifferent configured digital printing presses. At the same time, thecustomer gets the requested output quality, in this case the requestedoutput resolution, curing, or smoothing level. This offers a significantadvantage with regard to production consistency and customersatisfaction. Accordingly, configuring print products in such a mannermakes it possible for reproduction of the same job at another locationor on another device, while delivering the same quality results.

Embodiments of the invention go beyond a simple connectivity ofdifferent components of the digital workflow because very specificparameters, which are tightly coupled to the digital inkjet printingpress, are communicated among the various elements of the workflow.Currently, only the printer operator has control of these parametersbut, with the invention, such local printer adjustments become systemwide print job parameters that they are planned and used for printproduction.

Currently, wide format or super wide format ink jet printers can showactive print jobs at a machine control panel. The jobs are usuallyarranged in lists, queues, or workspaces (referred to herein as“workspaces”). Typically, workspaces are provided for jobs which have tobe printed, jobs which are printed already, as well additional printworkspaces and features for the printer operator to see and organize hiswork. Embodiments of the invention concern both changes on the printerand also the requirements for the RIP to make such a device and processactively monitorable and manageable. The base requirement is that abidirectional communication be established between the MIS, e.g. EFIPace, EFI Monarch, or EFI Radius, the production planning and schedulingsystem, e.g. EFI PrintFlow, the RIP, e.g. EFI Fiery XF, and the printer,e.g. EFI VUTEk GS 3250r or EFI R3225. This communication can be based ona standard, such as the CIP4 JDF (see www.cip4.org) or any otherproprietary implementation.

In an embodiment of the invention, the printer must be able to receivemessages or notifications. These could announce new print jobs orinclude changes or further information for already submitted jobs,reschedule the order of the jobs within the active print workspace,remove jobs from the active print workspace, etc. For each of thesemessages or notifications, the printer must exhibit an appropriateresponse. Therefore, the printer requires a receiver for receivingmessages from registered senders, an interpreter for understanding themessage or notification, and a translator from the communicationlanguage into the machine language. An active handler which performs theneeded modifications on the database, sends message to the printer UI orconnected applications, etc. is also needed.

In the opposite direction, the printer also must be able to sendmessages or notifications actively for all events which could happen.Such events include, for example:

-   -   New job arrived (received successful or failed);    -   Job starts printing;    -   Print progress updates;    -   Job is printed, including accounting parameters;    -   Job is canceled, including accounting parameters;    -   An error occurred while printing; and

Job deleted from the active workspace.

Furthermore, the printer has to communicate status information about theprinter itself, such as printing, idle, on maintenance, purging, etc.Therefore, the printer also requires changes in the user interface (UI)or at the data base to create an internal event at the printer side, theprovision of a listener that is waiting for the arrival of such eventsand that translates them into the communication language, and a senderthat submits the message to the registered receiver.

The print production planning and scheduling system receives thesemessages or update information and it updates the production planaccordingly. Any new print job which arrives at the scheduling system isscheduled and assigned to the printer that best matches the requirementsof the print job. The print job is added to the workspace so that thedifferent rules for optimizing the production process are fulfilled.These rules are related to the particular production planning andscheduling system or to the individual setting of the digital printingcompany.

Any change in the print job order creates an event which actively sendsupdate messages via the connected RIP to the printer. The workspace ofactive print jobs at the printer shows the job order in such a way thatit represents the production order of the production planning andscheduling system.

Events include, for example:

-   -   The information that a new job is ready for printing, which        creates an action on the printer side that it adds this job to        the defined place in the print job workspace;    -   The information that the order has to be changed, which creates        an action on the printer side to rearrange the job order in the        print job workspace; and    -   The information that a job has to be removed, which creates an        action on the printer side that the particular job is deleted        from the print job workspace, although actively removing of        print jobs from the workspace is not usually possible if this        job is currently printing.

The print workspace at the printer can be actively managed with theforegoing events. Any optimization of the production planning andscheduling system that is applicable to the print production processuses one or multiple of these events. This allows reducing, forinstance, the number of media changes because jobs which are using thesame media can be queued accordingly. The same is true for jobs whichrequest a particular ink set. This drastically reduces the make readytime for the print production, and also reduces the amount of waste onmedia and ink. Those skilled in the art will appreciate that, besidethese events described above, additional messages and updates can beimplemented.

Communication between the print production planning and schedulingsystem and the printer also includes the RIP and the MIS system. Aplanning and scheduling system for the print process is more useful fora larger printing company. Thus, if there are, for instance, twoprinters within a company which receive the print jobs from one RIP,then this RIP becomes the hub for these two devices. If the printproduction planning and scheduling system needs to move one job fromprinter (A) to printer (B), then this is managed from the RIP. The RIPreceives the information about this change from the planning andscheduling system, it sends the request for removing the job to printer(A), double checks if a new processing of the job is required for thedevice (B), prepares the new print data (if required), and sends the newor the original print data to printer (B). This job is added at therequested position to the workspace of active print jobs at printer (B).Therefore, the RIP must include a similar implementation of listener,receiver, translator, event handler, sender, etc. as describedhereinabove.

Each of the foregoing transactions includes not only the notification ormeta data, but also the content file. This further limits thepossibility of making errors.

If the company is bigger and has not just multiple printers, but alsohas multiple RIP systems, perhaps at multiple locations, the abovedescribed scenario also involves the MIS system when removing aparticular job from the printer (A) and the RIP (a) and moving it to theRIP (b) and the printer (B). Note that the print production planning andscheduling system is typically a part of the MIS or tightly coupled withthe MIS.

The foregoing capability makes it possible to avoid delays in productionbecause print jobs can be moved from a machine which is currentlyheavily used to a machine which is idle at the moment or which can offera slot for this production soon. This procedure is possible betweenmachines of the same type. In this case the re-ripping as describedhereinabove might be not required. This procedure is also possiblebetween machines of different types.

One advantage of the invention delivers this implementation in the caseof an unforeseen event. For example, if a printer is out of order andthe time frame until it is restored completely can not be foreseen, orthe printer is of a size that negatively impacts the delivery schedule,the waiting production at this machine can be rerouted to other deviceswithin the plant. This does not require any special communicationbetween the various equipment operators. Rather, the manager at theprint production planning and scheduling system can move the highpriority jobs to other devices and change the schedule for thesedevices, if required. All needed information and events are sent fromthis central place and the job workspace of the active print jobs on allinvolved printers is updated immediately. The jobs are removed from theprinter which is out of order, the RIPs produce new print files ifnecessary, and the print files are added at the correct places to theother printers as scheduled. For the printer operators, there is nochange on their regular work. They continue printing jobs in order asrequested and make sure that all of the print products are produced withthe requested quality.

The discussion below describes some of the features that are managed ina presently preferred embodiment of the invention, although thoseskilled in the art will appreciate that the invention may include otherfeatures.

White ink support: VUTEk GS printers, used in an exemplary embodiment ofthe invention, are capable of handling white as an extra colorant. Thereare different use cases for this extra colorant. For example, whileprinting on transparent media white can used as separation layer betweenthe front and the back side image, as layer to improve the image qualityfor backlight application, but also as a separate image layer to createspecific effects within the print product. DSF and MIS are now able todefine the usage of white ink as a job parameter. Beside the option tohandle separate white layers within the content files all specific whiteoptions from, for example, the Fiery XF RIP are supported:

-   -   White as spot color: The spot color of this name or alias from a        separated document prints white, i.e. white is handled as pure        spot color.    -   White mode Inked Image: Add white ink on every pixel which does        not have CMYK=0,0,0,0 on the printer side. The RIP takes the        maximum of all other colorants and applies this as white value.    -   White mode Bounding box: Add white ink on every pixel. The white        ink value can be defined within the JDF ticket, but it is fixed        for all pixels of the image.    -   White mode Inked Image Fix: Add white ink on every pixel which        does not have CMYK=0,0,0,0 on the printer side. The white ink        value can be defined within the JDF ticket, but it is fixed for        all pixels.    -   White mode inverse: Add white ink on every pixel which has        CMYK=0,0,0,0 on the printer side. The white ink value can be        defined within the JDF ticket, but it is fixed for all pixels.    -   White mode Optimized: Add white ink on every pixel accordingly        to the CMYK colorant values and the white point of the media.        This mode enlarges the gamut and makes a brighter output        possible.    -   White mode off: No white layer is created.

Status update to the planner: Producing SWF file format products (seewww.adobe.com/content/dam/Adobe/en/devnet/swf/pdf/swf_file_format_spec_v10.pdf) could take a while. Printing ten copies of a 5×5 meter banner cantake around 2.5 hours (VUTEk GS5000r printer with 600 dpi, CMYKcmyk modeand productivity of 96 m^2/hour). In an embodiment of the invention, theplanner module gets a status update after each and every copy. Thishelps the operator to see where the current production stays and whenthe start of the next production run could be expected.

Shorten time to production: The RIP delivers RTL files to the printers.These files include information which is mandatory for the correct printsetup of the machine and they also provide important information to theprinter operator. These use cases make it mandatory to parse the RTLfiles after they are downloaded on the printer side. Because these filesare large, i.e. the average size is related to the use cases between 1and 5 GB but also RTL files beyond 100 GB are not uncommon, this parsingis a time consuming effort. In an embodiment of the invention, the RIPdelivers all parameters but also the preview as part of thebidirectional communication to the printer. This allows skipping theparsing and showing the job immediately at the print station.

A Presently Preferred Implementation

The following provides a discussion of the integration of online anordering system, MIS, RIP, and printer in a detailed matter. Itdescribes the feature set of this development and in details the jobticketing between an EFI Fiery XF (RIP) and an EFI VUTEk printer and howto achieve that using JDF. Those skilled in the art will appreciate thatthe invention may be practiced with devices other than thosemanufactured by EFI (Fiery) and VUTEk, as well as with other protocolsthan those expressed by in the JDF specification.

The preferred integration is an http based JMF interface exposed by theprinter middleware. The discussion below primarily concerns a mostcomplex integration scenario DSF<->MIS<->RIP<->printer. Those skilled inthe art will appreciate that any subset of these types of devices worktogether using the same inventive technique disclosed and thusestablishes a similar integration level. Such subsets are, for example:

DSF—RIP—printer

MIS—RIP—printer

RIP—printer

Those skilled in the at will appreciate that the herein describedintegration details could be adapted to other MIS system and otherprinters as well.

The following provides an overview about goals which should be reachedwith this integration:

-   -   Building up an end-to-end, automated digital workflow solution;    -   Establishing a bi-directional communication between the        different systems of the workflow;    -   Monitoring the product status in the MIS and getting accounting        information back; and    -   Avoiding mistakes within the production by sending and applying        the product definitions automatically to the involved systems.

JDF is the standard job ticket within the printing process. It buildsthe base for the whole communication between the DSF, MIS, and RIP. Anembodiment of the invention creates a new link between the RIP and theprinter. Although the discussion herein concerns JDF, those skilled inthe art will appreciate that any known implementation would fulfill thetechnical requirements of this integration.

System Overview

FIG. 2 is a block diagram that shows JDF integration between the DSF(100), MIS (102), RIP (104), and production (106) facilities.

The DSF communicates with the MIS facility for:

-   -   Retrieving the device capabilities of the RIP and the printer;    -   Sending and responding to JMF commands and queries; and    -   Sending a JDF ticket for a created job in DSF via a JMF command.

The MIS sends to the DSF:

-   -   JMF Signals to a subscription URL specified by the MIS; and    -   JMF Signals to update the job status.

The MIS communicates via an MIS connect interface 30 with the JDFinterface 32 of the RIP for:

-   -   Retrieving the device capabilities of a JDF device configured in        the RIP;    -   Publishing an MIS media list to the RIP;    -   Sending JMF signals to a subscription for JDF commands; and    -   Sending JMF commands and queries.

The RIP sends to the MIS:

-   -   Device capabilities to publish the supported options of the        connected device;    -   JMF signals to a subscription URL specified by the MIS;    -   JMF signals to update the job status, device status, etc.; and    -   Accounting information, such as media and ink usage and printing        and processing time.

The RIP communicates via a plug-in or other interface 34 with the JDFinterface 36 of the printer for:

-   -   Retrieving the device capabilities of the printer;    -   Pushing an MIS media list forward to the printer; and    -   Sending JMF commands and queries.

The printer sends to the RIP:

-   -   Device capabilities to publish the supported options of the        connected device;    -   JMF signals to a subscription URL specified by the RIP;    -   JMF signals to update the job status, device status, etc.; and    -   Accounting information, such as media and ink usage and printing        and processing time.

The RIP downloads the content files for a given job from the URL sentfrom the MIS or DSF. The printer downloads the content files for thegiven job from the URL sent from the RIP.

FIG. 3 is a block schematic diagram that shows more detail ofRIP—printer integration. As can be seen, the printer comprises aLinux-based print system that includes the JDF adapter 36 for theprinter which, in turn, includes a JMF signal processor 40, JDFprocessing engine 42, and adapter 44. Those skilled in the art willappreciate that the printer need not be Linux-based. The print systemalso includes CORBA services 46 and a print database 48.

Generic Job Life Cycle

Even if every customer has its own specific workflow, a generic lifecycle of a product run would be as follows:

1. The customer describes the product in the DSF or any other online oroffline ordering system.

2. The print supplier selects a media type and a machine type for thisproduction based on the description from the customer within the MIS orwithin his ordering system; does a cost estimation based on the definedparameters, e.g. media, printer, quality, etc., and prepares aquotation; and estimates the production process within his schedulingsoftware and defines a possible delivery date.3. The customer accepts this quotation.4. The print supplier creates a job within the MIS and defines themachine, media, and ink set for this production; and optionallyschedules the production within his scheduling software.5. The MIS creates the job and sends a JDF to the RIP.6. The RIP receives the JDF job and downloads the content; andinterprets the JDF and creates a job in the RIP job list based on theprocessing parameters, such as:

-   -   Job name, Job ID, Description    -   Media information (media type, media size)    -   Ink set definition    -   Output parameters (size, duplex)    -   Numbers of copies    -   Color management parameters    -   Customer information (displayed within the RIP client)    -   Layout parameters, such as scaling, rotation, flip, mirror.

The RIP sets the priority for the processing based on the definedproduction schedule (due date); processes the job based on the JDFdefinition; sends status messages (JMF) back to the MIS; sends updatedJDF to the printer; and within a ReturnQueueEntry message, the RIPreports the processing time to the MIS.

7. The printer receives the JDF job and downloads the content (RTLfile); interprets the JDF and creates a job in the printer GUI job listbased on the processing parameters, such as:

-   -   Job name, Job ID, Description    -   Printer parameter as set within the RIP, e.g. Print mode,        Smoothing, etc.    -   Media information (media type, media size)    -   Ink set definition (already defined in the RTL job)    -   Output parameters (size, duplex)    -   Numbers of copies    -   Finishing information    -   Customer information

The printer sets the priority for the processing based on the definedproduction schedule (due date) and makes this information visible to theprint operator; prints the job based on the JDF definition; sends statusmessages back to the RIP (the RIP pushes the status update messagesfuture to the DSF or MIS); and within a ReturnQueueEntry message thefollowing audit information is sent:

-   -   Ink usage    -   Media usage    -   Printing time    -   Total number (number of goods and number of waste)

The printer closes the job and sends the JDF back to the RIP (the RIPcan update the JDF another time) and communicates the results future tothe MIS.

Description of the End to End Workflow

General

The resources such as media and ink must be synchronized between theMIS, RIP, and printer to achieve maximum automation. This also reducesthe possibility of manual errors in selecting the right resources andsetting the right attributes during the job ticket creation and transferprocess in an end-to-end workflow.

DSF/MIS—RIP—Printer

When all the three systems—MIS, RIP, and printer—are present in a printshop, the MIS assumes the manager role as far as resource management isconcerned. In a scenario when the MIS is newly added to an existingRIP-printer combination, all of the resources in the shop must be addedto MIS first and then they can be pushed to the RIP.

If the DSF is present and the MIS is absent, then the DSF assumes therole of the manager as far as resource management is concerned. If boththe DSF and MIS are present, then the MIS is the manager of resources.In the discussion below, the MIS is treated as the manager, although DSFalso fits into that role. Note the workflow description is also true ifthe DSF or another MIS takes over the manager role.

Resource Synchronization

Although it is ideal to have a fully automated workflow for thesynchronizing the media and ink resources across the three systems, insome case it is not practical. The steps below explain how the threesystems can synchronize media and inks to achieve a semi-automaticend-to-end workflow for job submission.

1. The MIS does a discovery of RIP servers on the print shop network.

2. Once it finds the RIP, the MIS pushes media and ink resources via aJMF Resource Command.

3. On receiving the MIS resources, the RIP adds them to its database.

4. The RIP also issues a JMF Resource Command to the printer to add theMIS media to its media database and MIS inks to its ink list with MISIds. The printer uses default settings for certain printer specificoptions because MIS or RIP operators may not be qualified to selectthose options.5. The RIP administrator then maps the MIS media to the RIP media setusing a mapping tool. The RIP sets its JDF device status as Not Ready.This prevents the MIS from sending KnownDevices or other JMFQueries/Commands. The MIS keeps retrying the query using a timer tocheck the RIP JDF device status.6. After the mapping is done, the RIP sets its JDF device status asReady and waits for the KnownDevices query from the MIS.7. The MIS administrator adds the discovered RIP device and sends aKnownDevices JMF query.8. The RIP finds the original MIS media from its map.9. The RIP also determines the ink set (CMYK or CMYKcmyk or CMYKcmykWetc.) from its media set corresponding to that MIS media.10. The RIP returns both the MIS media and ink set in the response tothe KnownDevices query as DevCaps.11. The MIS then associates these resources with the RIP JDF device thatwas registered with it. If the MIS operator chooses one of those mediaand ink resources for JDF Job submission to the RIP, the job runsautomatically through the RIP. Otherwise, a manual user intervention atthe RIP side is required.

Job Handling

1. Upon receiving a JDF job from the MIS, the RIP finds its media setfrom the map, processes the job, and creates the color managed RTL fileready to be printed.

a. The RIP detects the correct calibration set based on the build in mapof the MIS media and ink set combination. Another important parameterfor the detection of the correct calibration set is the quality, meansprint resolution.

For example:

i. The MIS has a media Vinyl_0021 this is mapped in the RIP to the medianame Vinyl; and

ii. The RIP has four different calibration sets (EPL+ICC profile) forVinyl:

1. Vinyl for the ink set CMYKcmyk with 600×360 dpi

2. Vinyl for the ink set CMYKcmyk with 1000×720 dpi

3. Vinyl for the ink set CMYK with 600×360 dpi

4. Vinyl for the ink set CMYK with 1000×720 dpi

iii. Based on the defined ink set and the quality mode within the MIS, acorrect detection of the calibration set is possible. That is, assumingthat the printer has, for example, two possible resolutions and twopossible ink sets, only one calibration set is available for eachcombination. If a certain combination is not available but requested fora specific job, the RIP stops the automatic processing and requests aoperator intervention.b. The RIP operator may create a nesting or a Step&Repeat job containingthe job sent by the MIS to save media. The RTL created by RIP is for thenesting or the Step&Repeat job.c. In the case of a nesting job, the RIP calculates an estimated inkvolume for each colorant in the original job sent by the MIS. That is,after the print run, media and ink usage information is provided to theRIP by the printer. Thus, the RIP builds the ratio between these volumesand the total volume for the whole nesting and saves those ratios intothe job ticket. The ratio of ink usage to media for each separate job isthen sent back to the MIS.d. For Tiling/Multi-page job, the RIP splits the original job sent bythe MIS into multiple parts and submits them separately to the printer.2. The RIP modifies the RunList resource URL in the JDF to point to thecreated RTL file and submits the JDF job to the printer.3. The printer JDF gateway creates a job in the printer with the ticketoptions specified in the JDF. For the printer specific options whichcannot be determined remotely in the MIS or RIP, the printer sets thedefault options.4. The printer operator opens the job in the UI, verifies the variousjob options, and overrides them if required.a. The printer operator may add the job sent by the RIP into a Queue orMulti-layer.b. As in the case of the RIP, for each color in the original RTL jobsent by the RIP, the printer calculates the ratio of that color in thequeue or multi-layer job created in the printer.5. After printing, the printer gathers the ink and media consumptionvalues.a. If it is a queue/multi-layer job, The printer calculates the mediaand ink consumption values for the original job sent by the RIP based onthe ratios determined above at step 4b.6. The printer then adds the media and ink consumption values along withthe MIS resource IDs to the AuditPool section of the JDF and sends thisback to the RIP as a RetunJDF Ticket.7. The RIP receives the JDF and performs the following calculations asrequired:a. If the job is a nesting job in the RIP, the RIP calculates the actualink consumption values for the original job sent by the MIS based on theratios saved above at step 1c. For media consumption, the RIP sends theratios of areas of each job in comparison with the area of the boundingrectangle of the nested job in the audit info. The MIS uses those ratiosto calculate the media cost for each job.b. If the job is a tiling/multi-page job in the RIP, the RIP adds themedia and ink consumption values for each part of the job submitted tothe printer separately.8. The MIS then determines the actual quantities of media and inks usedfor the original job and determines the costing.RIP—Printer

In the absence of a manager, such as the MIS or DSF in the workflow, theRIP acts as the manager. The steps below explain how the two systems cansynchronize media and inks to achieve a semi-automatic end-to-endworkflow.

1. Once the media sets are defined for the print device in the RIP, itissues a JMF resource Command to the printer to add the RIP media andinks to the print or database. The printer uses default settings forcertain printer specific options because the RIP operator may not bequalified to select those options.2. Once the job to be printed on printer is submitted to the RIP, itprocesses the job and creates the color managed RTL file ready to beprinted.3. The RIP creates a JDF ticket with the appropriate job options. Itsets the RunList resource URL in the JDF to point to the created RTLfile and submits the JDF job to the printer.4. The printer JDF gateway creates a job in the printer with the ticketoptions specified in JDF. For the printer specific options which cannotbe determined remotely in the RIP, the printer sets the default options.5. The printer operator opens the job in the UI, verifies the variousjob options, overrides them if required, and sends the job for printing.6. After printing, the printer gathers the ink and media consumptionvalues, adds them to the AuditTrail section of JDF and sends it back tothe RIP as a return JDF ticket.7. The RIP receives it and displays it in its client GUI.JDF/JMF Implementation DetailsOverview

The following discussion provides an overview of the JDF parameters andattributes for a presently preferred embodiment of the invention. Thoseskilled in the art will appreciate that these parameters and attributesare provided solely for purposes of illustration and example and not byway of limitation of the inventive subject matter herein disclosed.

1. Parameters sent from the DSF/MIS to the RIP and printer:

JobID, JobPartID

Media:

-   -   Definition of the media type    -   Definition of the media size        Ink (definition of the ink set)        Due date        Number of copies        Print quality (print resolution)        Finishing:    -   Special white ink printing (layer at the top, bottom or in        between or as special color)    -   Special clear ink printing (layer at the top or bottom or as        special color)    -   Grommet marks    -   Cut marks    -   Settings for contour cutting        Layout:    -   Size (scaling)    -   Center    -   x, y offsets    -   Mirroring (setting for printing on transparent medias)        Color management        Customer information        2. Parameters sent back to the MIS:        Media usage        Ink usage        Processing time        Printing time        Wastage of ink and media        3. Notification and queries sent to the RIP and printer:        Known devices query        Known messages        Resource Command        SubmitQueueEntry Command        ReSubmitQueueEntry Command        AbortQueueEntry        RemoveQueueEntry        QueueStatus        Subscription        4. Notification and queries sent to the MIS:        Status signals and return JDF        Device capabilities        Due Date

The due date parameter is an important parameter to signal the RIP andthe printer operator when a job has to be finalized and make it possibleto schedule the daily work correctly. This parameter becomes even moreimportant if the customer is planning its work with a scheduling system.At the RIP side, the due date has to have an influence on the processingpriority. This means that jobs with a sooner due date have to beprocessed earlier. At the printer side, it is information for theprinter operator to define his production runs properly. A colorindicator at the UI helps to see immediately which job is to be producednext.

Number of Copies

The number of copies parameter defines how many printouts the customerlikes to buy. It is also an important parameter to calculate at the endof a production how many good and waste printouts were made. In the DSFor MIS, the operator defines how many copies should be printed. If theRIP operator decides to place more than one copy at media to use theprinter more optimally, the number of copies parameter (better thenumber of print runs) sent to the printer is adapted automatically. Thesame happen at the printer side if the printer operator creates a layoutwith multiple copies from the same job.

Print Quality

The print quality parameter defines which output resolution has to beused. Based on this definition, the RIP chooses the correct calibrationset for the selected media or, if it is not available, shows a warningmessage to the operator.

The print quality defines the resolution of the RTL file. This parameteris not needed at the printer side.

Finishing

JDF supports a wide range of finishing parameters. One important set ofparameters are the cut and crop marks. The typical RIP supports a widerange of different mark types which have to be applied accordingly tothe JDF definition. This includes also the usage of grommet marks oreven settings for the creation of contour cutting information to cut theprintout afterwards at a cut table.

The marks parameter defines a specific content within the RTL file. Thisparameter is not needed at the printer side.

Another important parameter is the definition of an extra layer usingwhite or clear ink. (please see the discussion above).

Layout

The content might not have the size of the final print product. The DSFor MIS can define scaling as a layout parameter for a job or a finaldocument size. Apart from that, it is also possible to define thearrangement of the content at the media, e.g. x, y offsets, center onpage and if the job should be printed mirrored.

Layout parameters define the print ready output file from the RIP. Theyare not needed at the printer side.

Color Management

The MIS can define the usage of specific color management parameters.

Customer Information

This set of JDF parameters is used for sharing the information about thecustomer, e.g. name, address, etc. with the RIP and printer operator.

JMF Messages, Commands and Queries

Known Devices Query

The KnownDevice query message requests information about the devicesthat are controlled by a controller. The response is a DeviceList whichis list of DeviceInfo elements controlled by the controller thatreceives the query. In the case of RIP-printer integration, the printerJDF gateway acts as the Controller and the only device is the printer.

Known Messages

The KnownMessages query is used to request the supported JMF messagesfrom the connected JDF device. The KnownMessages query message returns alist of all message types that are supported by the RIP or printer JDFgateway.

Resource Query/Command

The resource command message is used to modify or create either globaldevice settings or a running Job. The resource query is used to request,e.g. the list of media or inks from the MIS. This integration has to useboth implementations.

SubmitQueueEntry Command

The SubmitQueueEntry command submits a job to a queue of a device orcontroller, RIP or printer. The QueueSubmissionParams provides theparameters of the submission

ReSubmitQueueEntry Command

A job is resubmitted to a queue using the ResubmitQueueEntry message.This allows late changes to be made to a job without affecting queueparameters and without exporting the internal structure of a queue.Resubmission overwrites the previously submitted job.

AbortQueueEntry Command

A submitted job can be aborted by the sender with the AbortQueueEntrycommand. Once this command is issued, the entry specified byQueueEntryDef is aborted and remains in the queue withQueueEntry/@Status=“Aborted”.

RemoveQueueEntry Command

This command causes the entry specified by QueueEntryDef to be removedfrom the queue. It does not affect QueueEntry [@Status=“Running” or@Status=“Suspended”]. Use AbortQueueEntry to stop a running or suspendedjob and then remove it with RemoveQueueEntry. The RemoveQueueEntry eventfrom the MIS should remove the job from the RIP and the printer queue.

QueueStatus Message

The QueueStatus message request or returns the status of queue.

Subscription

Queries and commands are subscribed for using subscription elements.

Request

The DSF and MIS uses global subscriptions for requesting queue or devicestatus updates. Apart from that, they subscribe on a job level for jobstatus updates

Status Signals and Return JDF

The RIP provides the following status to the MIS. The information inbrackets shows at which the RIP job status this message is sent:

TestRunInProgress (set during job analysis)

Ready (at any stable RIP job state, e.g. previewed, ripped, etc.)

InProgress (while processing, e.g. ripping, printing)

Completed (after job completion, e.g. printed, verified)

FailedTestRun (job processing errors out)

Suspended (job got canceled)

Aborted (job got aborted)

Once the subscription for QueryStatus query is done, the Signals aresent back by the printer JDF.

Device Capabilities

On receiving GetKnownDevices query, the JDF enabled device sends theresponse back with all the device capabilities it can support.

ReturnQueueEntry Message

The printer returns the audit information once the job was printedsuccessfully. The ReturnQueueEntry message to the RIP is sent every timea print run finished or ended, and the job on the machine side movesfrom the active print queue into the done queue. At this time, the JDFconnector at the machine side sends a ReturnQueueEntry including all thesum up audit information (media and ink consumption, printing time,wastage, good and bad copies) for this particular print run. This is thecase within the following scenarios:

-   -   The requested number of printouts were completed, e.g. ten of        ten requested copies are printed);    -   The printer operator changed the number of copies within the UI,        e.g. the MIS requested ten copies, the operator changed the        number of copies to five and these five copies were printed.        This could happen upfront or during the printing; and    -   The printer operator hits an E-Stop or cancelled the job        differently.

The printer operator has the ability to move a completed job back intothe active print queue and print another number of copies. This could berequired for the following reasons:

-   -   To reprint the job because some of the previously printed copies        are not in an acceptable shape;    -   To finalize the print run and complete the requested number of        copies; and    -   To restart the previously stopped or cancelled print run.

After the additional print run ends, the ReturnQueueEntry message to theRIP is sent again.

The JDF connector sums up all audit information (media, ink, printingtime) for the number of copies within a print run. The number of copiesis independent of the requested number of copies. If theReturnQueueEntry message was sent and the printer operator starts theprint run again, the audit information is added and the complete RQE issent again to the RIP. If the printer operator changes the media on themachine after a job was already printed, a second section in the RQE isadded which counts individual media usage and the number of print runs.This accumulation starts from 0.

Use Cases

Simple and Combined Jobs

General

A simple job is based on one content file which is ripped and printedwithout any variation on the layout. The feature set of the involvedsoftware products allows the user to make various changes on the layoutto save media or fulfill the product requirements. It is possible toplace multiple jobs (known as nesting or layout) or multiple copies of asingle job (known as S&R or layout) at one sheet or to split a job toget it printed on multiple sheets (known as tiling). All of thesechanges have an impact how the accounting parameters can be calculatedand transmitted accurately. One goal of the invention is to handle thesejob types correctly without any manual user interaction and keep all ofthis specific logic at the places where the combining or adaptation of aparticular job happened.

RIP

If the operator at the RIP combines for instance two JDF jobs to onenesting and send this over to the printer for printing. The printertreats this job as a single print job and delivers the job status andthe accounting parameters or the nesting job back. The RIP must splitthese values using the following routine:

-   -   While ripping, the file the RIP is counting the droplets for        each and every colorant of each individual job.    -   The RIP builds a ration of the sum of the droplet count of the        individual job for a single colorant and the droplet count of        the complete nesting for this colorant. This ratio is stored in        the specific job ticket.    -   The JDF signals, as with status updates, are communicated to the        DSF or MIS for each ganged job separately.    -   If the ink usage is communicated back from the printer, the RIP        splits each individual colorant by the calculated ratio and use        the results as ink usage parameters for the back communication        to the DSF or MIS.    -   The media usage is calculated simultaneous by using the ratio of        the individual job size to the nesting job size.        Printer

If the operator at the printer combines two or more jobs to a layout,the calculation of the media and ink usage for each individual job issimilar to the description above. The printer splits the accounting databased on the previously created ration and delivers it separated back tothe RIP and MIS. The printer splits these values using the followingroutine:

-   -   During the job detection the printer is counting the droplets        for each and every colorant of each individual job.    -   The printer builds a ration of the sum of the droplet count of        the individual job for a single colorant and the droplet count        of the complete layout for this colorant. This ratio is stored        in the data base for the individual job.    -   The JDF signals, as with status updates, are communicated to the        RIP for each ganged job separately.    -   After the printing process is completed, the printer splits each        individual colorant by the calculated ratio and uses the results        as ink usage parameters for the back communication to the RIP        and MIS.    -   The media usage is calculated simultaneously by using the ratio        of the individual job size to the layout job size.        Media Handling        General

Media is a complex attribute in the JDF because a correct definitionrequires several parameters. There are even different meanings of mediawithin the DSF/MIS, RIP, and at the printer. The MIS uses it as aninventory item. In the RIP, the media is a virtual definition for acalibration set (EPL+ICC profile) and, at the printer side, it is aphysical print substrate. To sync up all of these different meanings ofmedia a mapping is needed.

DSF/MIS—RIP

The DSF or MIS submit the media catalog to the RIP via JMF resourcecommands. At the RIP side, the mapping between the different DSF/MISmedia definitions and the available calibration sets is an administratorand setup task.

It is likely that the RIP operator creates multiple calibration sets forone media. They differ in the printing resolution, half toningalgorithm, ink set, or black generation setting, and a given media nameis often used for distinguishing them within a long list of calibrationsets. For this integration, is it mandatory that calibration sets forthe same physical media have the same media name within the RIP.Otherwise the media mapping does not work as described above.

To setup the RIP correctly, the RIP needs the DSF or MIS list of mediaavailable for specific device types. The device type must be implementedin the queries and commands to differentiate the media, e.g. by formats(Fiery versus VUTEk, for example). The DSF or MIS must send JMF resourcecommands whenever a media is added, a media definition is changed, or amedia is deleted from its database.

All received media must be added to an internal map within the RIP andpushed further to the printer. This map builds the link between theentries in the DSF or MIS media database and the available calibrationsets (media types) of the selected printer. Therefore, a manual processis needed in which the RIP operator defines the link between the MISmedia and the proper RIP media type. This has to happen during setup ofthe RIP, but can be redone whenever it is needed. This mapping is usedfor all RIP output devices from the same type, e.g. GS printer.

While setting up a new output device for which the RIP operator has notcreated a mapping, the RIP does not poll or request a media catalog fromthe MIS/DSF. Rather, the media catalog is sent to the RIP by theMIS/DSF. The DSF or MIS sends a JMF command to the RIP whenever theoperator adds, changes, or deletes a media definition. The RIP informsthe operator with a visual indicator that the media definition isupdated. It is the responsibility of the RIP operator to check theupdate and adapt the media mapping to the new media definition.

While processing, the RIP uses the created map to select the correctcalibration set (EPL+ICC profile) based on information from the DSF orMIS. The map defines the link between the DSF or MIS media and the RIPmedia type. Based on the additional JDF information, such as ink set,resolution (quality) and the half toning algorithm, the requestedcalibration set is selected and used for the creation of the print data.

It is a common procedure for the RIP operator to review and change thecalibration set manually at the beginning of the RIP process.Independently, if the RIP operator uses the requested calibration set orchanges it, the audit information inform the DSF and the MIS which mediaand which ink were used.

The defined size of the media is also taken from the JDF and used withinthe RIP for layout and processing of the job.

RIP—Printer

At the printer side the DSF or MIS, media definitions are added to themachine database. FIG. 4 shows a mapping tool for media. Mediadefinitions are kept in a table (see Table 1 below) table and keeping itin sync with the definition of the media catalog in the MIS and RIP isimportant. The media definition within the database requires thefollowing parameters:

TABLE 1 Media definition within the printer Parameter Data Type ValuesName Text <value> Width Double <value> Length Double <value> ThicknessDouble <value> Cost Double <value> Vacumm Enum <value> Type Enum websheet clear web clear sheet Shutters Enum none single double post LampsEnum low medium high max custom Custom_Cure_Intensity Integer <value>

The printer exposes these as custom JDF attributes for the mediaresources in the DevCaps to the RIP. The RIP displays them in thespecial tab for showing the settings for the given printer.

Defining the media in the printer database should happen during setup ofthe printer because, otherwise, only the default definitions areavailable. During the setup process at the RIP side, the retrieved mediainformation is transferred towards the printer via a JMF command. Theprinter adds the new media definition automatically to the databaseafter receiving the JDF command. Note that the parameter list for amedia definition includes some media and printer specific parameters.The database entry is built without them and the machine operator addsor corrects it while working with it.

If the MIS sends a JMF command to the RIP after the operator at the MISside added or changed a media definition, the RIP forwards this JMFcommand to the printer. This command forces an update of the database asdescribed above.

Ink Handling

General

The correct handling of ink is important for the correct backcommunication of ink usage. One can distinguish between the definitionof the ink set, e.g. if the printer should run in CMYK mode or if theadditional light inks have to be used too and the definition of theusage of additional colorant, such as white or clear ink.

DSF/MIS—RIP

The printer and RIP inform the DSF and MIS about the possible ink setsat the printer within the device capabilities. For GS printers, CMYK andCMYKcmyk ink sets are possible. The printing of white ink is an option.T

The MIS defines the ink set for the output production. The RIP processesthe job according to this setting. This means that the propercalibration set (EPL+ICC profile) must be used to create the correct RTLfile. The MIS uses a description of the inks as specified as part of theprint run. For the RIP, it is a requirement that, e.g. black is treatedas black and not marked as an inventory number or any other description.At the printer side, the correct definition of the ink, e.g. name,vendor or ID, along with the pure color name, is important. This becomesimportant if different inks are available and the operator needs to takecare to choose the correct ink for the particular print run.

RIP—Printer

On the printer side, the RTL file defines the used ink channels so thereis no need to distinguish between a CMYK or CMYKcmyk ink set. Even theusage of additional colorants is taken out of the RTL file. Jobs whichrequest an ink set that is not supported error out at the printer side,e.g. a job with white ink is send to the printer without white inksupport

Content Handling

DSF/MIS—RIP

The DSF and MIS send the link to the content as URL. It is importantthat the location is accessible from the RIP side. This is because theRIP server is running as a service and it might be required to set upthe user rights correctly to make a download of the content filepossible. The RIP should be capable of supporting multiple content fileswithin on JDF.

RIP—Printer

Printing on, for example, a GS printer is a time critical issue. Manyprocesses run in real time. Therefore, it is not possible to interferethese processes with the up- or download of content files. To fulfillthis requirement, the RIP writes the content file either at a sharedlocal folder at the RIP workstation, or at a shared network location,and sends the URL within the JDF to the printer. The printer downloadsthe content whenever it is safe for the printing process.

To avoid a significant delay between the finalization of the ripping atthe RIP side and the appearance of the job within the UI, the RIPprovides a preview with the JDF ticket. After arriving of theSubmitQueueEntry command, the printer process the JDF and can add thejob immediately to the job list in the UI. As long as the content is notdownloaded to the printer, the printing of the job is not possible.

Audit Information: Media, Ink Usage, Printing Time

Unit of Measurements

Following are the units of measurements for the different auditinformation:

-   -   Media length: points    -   Area coverage: square points    -   Ink: liter        Media Handling

The printer delivers:

1. The printed length (L)

2. The printed square feet (SQF)

3. The number of print runs (PR), e.g. ten copies are needed. Theoperator placed two per sheet. PR=5, equivalent for roll)

4. Number of copies (N)

For the particular job, it is known if it needs to be printed or roll orsheet media and:

1. Media width (w)

2. Media length for sheet (I) for roll this is the total length of theroll but not needed below.

Here are the different scenarios:

1. Printer runs on sheets. One or multiple copy per sheet.

a. Inventory management: PR defines the number of used sheets.

b. Used media: SQF represents the used media for production

c. Waste: ( ) (size of the sheet multiplied with the number of printruns reduced by the printed square points)

2. Printer runs on roll media. one roll, with or without layout (jobsare located after each other or two or more jobs are located beside eachother)

a. Inventory management: L defines the length of used roll media.

b. Used media: SQF represents the used media for production.

c. Waste: ( ) (width of the roll multiplied with the printed lengthmultiplied with the number of print runs reduced by the printed squarepoints).

3. Printer runs on roll media. Multiple rolls (up to three), layout (twoor more jobs are located beside each other)

a. Inventory management: L defines the length of used roll media.

b. Used media: SQF represents the used media for production.

c. Waste: ( ) (width of the roll multiplied with the printed lengthmultiplied with the number of rolls multiplied with the number of printruns reduced by the printed square points).

For sheet media, the number of used sheets is reported back. For rollmedia the media length is reported back in points. In both cases thearea coverage is reported back in square points.

If a job has to be reprinted, the ReturnQueueEntry message includes asecond ResourceAudit for media and ink usage. The amount of ink andmedia usage for the second print run sum up the values from the previousprint runs.

If the printer operator exchanges the media in-between two print runs,then the counting for the media usage starts from zero again. The ID forthe new media is tracked in the ReturnQueueEntry message.

Ink handling

Ink usage is reported back in liters.

Time handling

The printing time is reported back in JDF conform dateTime format

RIP—Printer

The transactions between the RIP and printer are based on the JMFstandard. The most relevant JMF commands and queries that need to beimplemented by printer are defined above with examples of Requests andResponses. There are many more JMF messages as per the JDFspecifications.

MIS Job Ticket

The DSF and MIS include a hyperlink (URL) to the JDF job ticket. The RIPand the printer user interface display this link within the jobinformation. The operator could open up the job ticket in a Web browserto get additional information about the current job. For all MIS's thatdo not support a Web-based interface, this URL could point to a jobticket within a PDF format. The RIP or the printer operator opens it toget the complete overview about additional settings at the MIS side.

Print Ready Job Creation

Another use case is the creation of a print ready job within the DSF,MIS, and RIP software products to avoid any additional user interactionfrom the print operator at the machine apart from the pure printingtask.

Multi Layer Definition

At the UI it is possible to arrange different jobs in such a way toprint them above each other with the ability to add a black or a whitelayer in between. This feature is mainly used to print on transparentmedia. To define the order but even the content of each individual printrun we use the JDF technique of defining product parts separately.

Multi Roll Setup

The GS5000 printer, for example, prints on two or more media rolls atthe same time. Therefore, the operator at the UI must arrange the jobscorrectly so that the placement of the job fits with the media position.

Print Options

The VUTEK GS printer, for example, sends special print options withinthe device capabilities to the RIP. The RIP client displays them withinthe printer special tab. The RIP operator can make settings here and thecreated JDF ticket transfers them to the printer.

Table 2 lists some print options. These parameters are important in anautomated workflow environment in which the job arrive print ready atthe printer and no manual interactions of the print operator arerequired.

TABLE 2 Print Options Parameter Prerequisites Comments Printing ModeValues: Bidirectional: Prints while carriage Bidirectional moves in bothdirections Unidirectional Unidirectional: Prints while carriage movesfrom right to left Interlace Mode Values: Multipass Standard: StandardMultipass Standard interlacing levels. Single Pass Standard Single PassStandard: ½ the Multipass High interlacing levels as Multipass MultipassDouble Strike Standard. Multipass Ultra High Multipass High: 2X theinterlacing levels as Multipass Standard. Multipass Double Strike: 2Xthe data levels as Multipass Standard. Multipass Ultra High: 3X theinterlacing levels as Multipass Standard. Carriage Speed Values: Speedat which Carriage travels while Standard printing. Max Standard: 62inches/second (52 inches/second for high-res) Max: Maximum speed (62inches/second). Smoothing Values: Each smoothing level will increase theNone amount of interlacing, producing Light higher quality print fromlowest to Heavy highest Curing Values: % of Lamp Power to be used on Lowcuring: Medium Low: 40% High Medium: 60% Max High: 80% Custom Max: 100%Custom: User defined % Shutter Mode Values: Single: Trailing Lampshutter will open Single following each pass Double Double: Both Lampshutters will open Post on each pass Post: First Lamp shutter will openon each pass curing the previous pass Full Bleed Binary state Bleeds theimage over the edge of the media Add Header Binary state Adds headerinformation as defined in VUI Add Footer Binary state Adds footerinformation as defined in VUI Center Binary state Centers the image onthe media Mirror Binary state Mirrors the image. The image prints fromright offset (rather than the left on a regular print), then flips theimageDashboard and Notification Support

In an embodiment of the invention, the RIP herein can be thought of as aserver that can drive many inkjet printers from different vendors.Hence, the RIP can be used as a centralized provider of a dashboard andnotifications for all the printers that are connected to it. In anembodiment of the invention, there may be multiple RIP servers in aprint shop driving multiple printers and/or proofers. FIG. 5 is a blockschematic diagram that shows a system architecture that supports adashboard and notification services according to the invention. In FIG.5, the acquisition function 100 communicates with the RIP 104 via adashboard agent 50. The RIP, in turn communicates with the productionfunction 106 (see, also, FIG. 1).

Notifications Setup Workflow

Registration, installation, and configuration of the dashboard andnotifications function should be seamless for a RIP administrator. Inthe presently preferred embodiment of the invention there are twoscenarios of interest (see FIGS. 6-8):

-   -   A customer, who has a RIP driving two or more printers, just        bought a dashboard license. How can notifications be set up for        the printers from RIP easily, i.e. without having to go to        different machines/web sites; and    -   A customer, who already has a dashboard license, wants to set up        notifications for a new printer in the RIP.

FIG. 6 is a screen shot showing a dialog for printer setup in a RIPaccording to the invention.

FIG. 7 is a screen shot showing a first step in dashboard registration,agent installation and notifications setup according to the invention.FIG. 7 shows the first scenario above, where the customer has justpurchased a dashboard license.

FIG. 8 is a screen shot showing notifications setup where a dashboardlicense has already been purchased and installed according to theinvention. Thus, FIG. 8 shows the second scenario above, where thecustomer has just already purchased and installed a dashboard licenseand want to set up notifications.

FIG. 9 is a block schematic diagram showing a dashboard andnotifications workflow according to the invention. In FIG. 9, thedashboard server 51 is shown interfacing operators and a dashboard HTMLuser interface to the dashboard agent 50 which, in turn, is incommunication with one or more RIPs 104 via the RIP client 32.

One requirement for supporting dashboard and notifications is that theRIP should have bi-directional communication with the printers.Notifications, such as emails and SMSs are only sent via the dashboard.The dashboard server uses a notifications server for email and SMSdelivery. Notifications are generated for each printer that is incommunication with the RIP.

Notifications are job-centric. In an embodiment of the invention,printer failures and warnings are piggybacked to job statusnotifications. For example, a notifications might be provided asfollows:

-   -   “Printing of Job ABC failed on VUTEk GS 3250 due to the        overheated lamps”        or:    -   “Printed Job XYZ successfully on VUTEk GS 5000r. Magenta Ink        level is low, please refill.”

This approach ensures that customers do not receive too many printerfailure and warning alerts when the printer is not actually printing ajob.

Dashboard User Interface

FIGS. 10-14 show a dashboard user interface according to the invention.In embodiments of the invention, the dashboard shows printer relateddata, such as performance, utilization, and statistics (see FIG. 10);job and consumable related data, such as jobs and costing, ink usage,area printed by media type, and jobs printed by media type (see FIG. 11,in which the dashboard displays consolidated material cost incurred forthe selected time period and printers, where cost is calculated based onconsumed media and ink, and where such data is entered by the user andstored in the dashboard; in this example, the user can change thecosting by using the “Edit Costing” link in the dashboard and the joblist can be viewed by clicking on any item within the dashboard); jobs(see FIG. 12); and material costs (see FIGS. 13 and 14).

Computer Implementation

FIG. 15 is a block schematic diagram that depicts a machine in theexemplary form of a computer system 1600 within which a set ofinstructions for causing the machine to perform any of the hereindisclosed methodologies may be executed. In alternative embodiments, themachine may comprise or include a network router, a network switch, anetwork bridge, personal digital assistant (PDA), a cellular telephone,a Web appliance or any machine capable of executing or transmitting asequence of instructions that specify actions to be taken.

The computer system 1600 includes a processor 1602, a main memory 1604and a static memory 1606, which communicate with each other via a bus1608. The computer system 1600 may further include a display unit 1610,for example, a liquid crystal display (LCD) or a cathode ray tube (CRT).The computer system 1600 also includes an alphanumeric input device1612, for example, a keyboard; a cursor control device 1614, forexample, a mouse; a disk drive unit 1616, a signal generation device1618, for example, a speaker, and a network interface device 1628.

The disk drive unit 1616 includes a machine-readable medium 1624 onwhich is stored a set of executable instructions, i.e., software, 1626embodying any one, or all, of the methodologies described herein below.The software 1626 is also shown to reside, completely or at leastpartially, within the main memory 1604 and/or within the processor 1602.The software 1626 may further be transmitted or received over a network1630 by means of a network interface device 1628.

In contrast to the system 1600 discussed above, a different embodimentuses logic circuitry instead of computer-executed instructions toimplement processing entities. Depending upon the particularrequirements of the application in the areas of speed, expense, toolingcosts, and the like, this logic may be implemented by constructing anapplication-specific integrated circuit (ASIC) having thousands of tinyintegrated transistors. Such an ASIC may be implemented with CMOS(complementary metal oxide semiconductor), TTL (transistor-transistorlogic), VLSI (very large systems integration), or another suitableconstruction. Other alternatives include a digital signal processingchip (DSP), discrete circuitry (such as resistors, capacitors, diodes,inductors, and transistors), field programmable gate array (FPGA),programmable logic array (PLA), programmable logic device (PLD), and thelike.

It is to be understood that embodiments may be used as or to supportsoftware programs or software modules executed upon some form ofprocessing core (such as the CPU of a computer) or otherwise implementedor realized upon or within a machine or computer readable medium. Amachine-readable medium includes any mechanism for storing ortransmitting information in a form readable by a machine, e.g., acomputer. For example, a machine readable medium includes read-onlymemory (ROM); random access memory (RAM); magnetic disk storage media;optical storage media; flash memory devices; electrical, optical,acoustical or other form of propagated signals, for example, carrierwaves, infrared signals, digital signals, etc.; or any other type ofmedia suitable for storing or transmitting information.

Although the invention is described herein with reference to thepreferred embodiment, one skilled in the art will readily appreciatethat other applications may be substituted for those set forth hereinwithout departing from the spirit and scope of the present invention.For example, a person skilled of the art would appreciate that theprinter may be configured to send status messages directly to theplanning and scheduling system, the management information system (MIS),and/or the digital store front (DSF) directly, rather than, or inaddition to, sending messages to the RIP. For further example, a personskilled in the art would appreciate that there are at least twodifferent cases of applying changes to a print job after the print jobis submitted, i.e. the print job is updated, but remains at the statewhich it reached, e.g. the number of copies is changed; and the printjob is to be rerouted, which requires removing the print job from thecurrent position and resubmitting it either with different parameters,such as a new calibration set, or even sending it to another RIP orprinter if the current RIP or printer is busy or not available.

Accordingly, the invention should only be limited by the Claims includedbelow.

The invention claimed is:
 1. A printing workflow system, comprising: araster image processor (RIP) comprising a hub for establishing andmaintaining communication, via messages having a common format, ofmultiple combinations of printer specific parameters between a planningand scheduling system and a plurality of printers lacking activemonitoring and management functions, each of the plurality of printersassociated with a printer interface comprising a printer adapter thatestablishes such active monitoring and management functions, saidprinter adapter configured to actively send messages to said RIP in thecommon format and translate messages received from the RIP from thecommon format into a printer specific machine language; wherein messagesreceived from said plurality of printers announce features and optionsavailable at said plurality printers to said RIP, and wherein said RIP,actively announces the received features and options of said pluralityof printers to said planning and scheduling system, and wherein theannounced features and options available at said plurality of printersare presented via a user interface at said planning and schedulingsystem; wherein options selected, via said user interface at saidplanning and scheduling system, are sent to a particular printer of saidplurality printers, via said RIP, with a print job as printer specificjob parameters, wherein said particular printer is assigned by saidplanning and scheduling system to execute the print job based on theannounced features available at said particular printer, the print jobsent in the common format; and wherein a limitation of said particularprinter is known in advance and only printing options that are availableat said particular printer can be selected in jobs sent to saidparticular printer.
 2. The system of claim 1, further comprising: aprocessor implementing a digital store (DSF) front comprising amanagement facility for receiving requests for quotes (RFQ),specifications (SPECS), files; and for providing payment and reorderinformation, catalog information, pricing, status, and invoices.
 3. Thesystem of claim 1, further comprising: a processor implementing amanagement information system (MIS) for providing job and systemmanagement, planning, reporting, and scheduling; wherein said MISprovides schedule and job information, specifications, and files to apreparation function and receives status and cost information from saidpreparation function.
 4. The system of claim 1, further comprising: aprocessor implementing a preparation function, interacting with saidmanagement function, for providing proofing and photo work and advancedworkflow, automated preflight, RIP, and color management functions; saidpreparation function providing one or more job tickets for use inconnection with a production function for providing schedule and jobinformation, specifications, and files to said production function andfor receiving status and cost information therefrom.
 5. The system ofclaim 1, further comprising: said management function, responsive to auser, defining and identifying full media parameter configurations. 6.The system of claim 1, further comprising: said management function,responsive to a user, associating a particular price to a particularprint option, product, or product quality.
 7. The system of claim 1,further comprising: said management function, responsive to a user,configuring a pricing schema wherein different prices are provided for,and are related to, a particular selected output quality.
 8. The systemof claim 1, wherein said common message format comprises CIP4 JDF. 9.The system of claim 1, said printer adapter comprising: a receiver forreceiving messages or notifications from registered senders; aninterpreter for interpreting a message or notification; a translator fortranslating said messages or notifications from a communication languagein said common format into a printer machine language; and an activehandler for modifying a printer database to create an internal event atsaid printer, and for sending messages to a printer UI or connectedapplications.
 10. The system of claim 9, said printer adapter activelysending messages or notifications from said particular printer forevents that include any of a new job arrived (received successful orfailed); a job starts printing; print progress updates; a job isprinted, including accounting parameters; a job is canceled, includingaccounting parameters; an error occurred while printing; and a job isdeleted from an active workspace.
 11. The system of claim 9, saidprinter adapter communicating printer status information to said RIPincluding any of printing, idle, on maintenance, and purging.
 12. Thesystem of claim 1, said planning and scheduling system receivingmessages or update information and updating a corresponding productionplan accordingly; wherein any new print job which arrives at saidplanning and scheduling system is scheduled and assigned to a printerthat best matches requirements of said print job; and wherein a printjob is added to a workspace to fulfill different rules for optimizing aproduction process, wherein said rules are related to a particularproduction planning and scheduling system or to an individual setting.13. The system of claim 1, wherein any change in said print job createsan event which actively sends update messages via said RIP to saidparticular printer; wherein a workspace of active print jobs at saidparticular printer shows job order to represent a production order ofsaid planning and scheduling system.
 14. The system of claim 1, saidmessages comprising one or more events that include any of informationthat a new job is ready for printing, which creates an action on saidparticular printer that adds a job to a defined place in a print jobworkspace; information that an order has to be changed, which creates anaction on said particular printer to rearrange a job order in said printjob workspace; and information that a job has to be removed, whichcreates an action on said particular printer that a particular job isdeleted from said print job workspace.
 15. The system of claim 1,wherein upon receiving information about a printer change from theplanning and scheduling system, said RIP sends a request for removing ajob to a printer currently responsible for said, determines if a newprocessing of the job is required for a printer to which the job is tobe moved, prepares new print data for the job if required, and sends thenew or the original print data to the printer to which the job is to bemoved; wherein the job is added at a requested position to a workspaceof active print jobs at the printer to which the job is to be moved. 16.The system of claim 1, further comprising: multiple RIP systems incooperating communication for moving print jobs from a printer which iscurrently heavily used to a printer which is idle or which can offer aslot for production soon.
 17. The system of claim 1, said printeradapter comprising: an http based JMF interface exposed by a printercontrol system.
 18. The system of claim 1, comprising: a digital storefront (DSF) communicating with a management information system (MIS) forretrieving print capabilities of the RIP and the plurality of printers,sending and responding to commands and queries, and sending a ticket fora created job in the DSF via a command.
 19. The system of claim 1,comprising: a management information system (MIS) sending to a digitalstore front (DSF) signals to a subscription URL specified by the MIS andsignals to update job status; said MIS communicating via an MIS connectinterface with an interface of the RIP for retrieving print capabilitiesof a printer configured in the RIP; publishing an MIS media list to theRIP; sending signals to a subscription for commands; and sendingcommands and queries.
 20. The system of claim 1, comprising: said RIPsending to a management information system (MIS) print capabilities topublish supported options of said plurality of printers, sending signalsto a subscription URL specified by the MIS; sending signals to updatejob status and device status; and sending accounting informationcomprising any of media and ink usage and printing and processing time;said RIP communicating via said printer interface of each of theplurality of printers for retrieving capabilities of the plurality ofprinters, pushing an MIS media list forward to the plurality ofprinters, and sending JMF commands and queries; said plurality ofprinters sending to the RIP print capabilities to publish supportedoptions of said plurality of printers, sending signals to a subscriptionURL specified by the RIP, sending signals to update job status anddevice status, and sending accounting information comprising any ofmedia and ink usage and printing and processing time; and said RIPdownloading content files for a given job from a URL sent from the MISor from a digital store front (DSF); wherein a printer assigned saidgiven job downloads said content files for said given job from a URLsent from the RIP.
 21. A printing method, comprising: providing a rasterimage processor (RIP) comprising a hub for establishing and maintainingcommunication, via a message having a common format, of multiplecombinations of printer specific parameters between a planning andscheduling system and a plurality of printers lacking active monitoringand management functions, each of the plurality of printers associatedwith a printer interface comprising a printer adapter that establishesactive monitoring and management functions, said printer adapterconfigured to actively send messages to said RIP in the common formatand translate messages received from the RIP from the common format intoa printer specific machine language; wherein messages received from saidplurality of printers announce features and options available at saidplurality of printers to said RIP, and wherein said RIP, activelyannounces the received features and options of said plurality ofprinters to said planning and scheduling system, and wherein theannounced features and options available at said plurality of printersare presented via a user interface at said planning and schedulingsystem; wherein options selected, via said user interface, at saidplanning and scheduling system are sent to a particular printer of saidplurality of printers, via said RIP, as printer specific job parametersalong with or subsequent to sending a print job, wherein said particularprinter is assigned by said planning and scheduling system to executethe print job based on the announced features available at saidparticular printer, the print job sent in the common format; and whereinsaid particular printer's limitations are known in advance and onlyprinting options that are available at said particular printer can beselected in jobs sent to said particular printer.
 22. A printer adapterfor establishing active monitoring and management functions for aprinter otherwise lacking such active monitoring and managementfunctions, comprising: a receiver for receiving messages ornotifications, in a common format, from registered senders via a rasterimage processor (RIP) comprising a hub for establishing and maintainingcommunication, via messages having the common format, of multiplecombinations of printer specific parameters between any of a digitalstore front and a planning and scheduling system and said printeradapter; an interpreter for interpreting said received messages ornotifications, wherein said received messages and notifications includeprinter specific job parameters sent along with or subsequent to a printjob, said printer specific parameters based on options selected, via auser interface, at any of said RIP, said digital store front, or saidplanning and scheduling system; a translator for translating saidmessages or notifications from a communication language in said commonformat into a printer machine language; an active handler for modifyinga printer database to create an internal event at said printer, and forsending messages to a printer UI or connected applications; and a senderfor actively sending messages in the common format that announcefeatures and options available at said printer to any of said digitalstore front and said planning and scheduling system, via said RIP,wherein the announced options available at said printer are presentedvia said user interface, and wherein the announced features are used bysaid planning and scheduling system to assign said print job to saidprinter, via said RIP.
 23. A printing workflow system, comprising: araster image processor (RIP) comprising a hub for establishing andmaintaining communication, via a message having a common format, ofmultiple combinations of printer specific parameters between: a digitalstore front (DSF) comprising a management facility for receivingrequests for quotes (RFQ), specifications (SPECS), files; and forproviding payment and reorder information, catalog information, pricing,status, and invoices; and a plurality of printers lacking activemonitoring and management functions, each of the plurality of printersassociated with a printer interface comprising a printer adapter thatestablishes such active monitoring and management functions, saidprinter adapter configured to actively send messages to said RIP in thecommon format and translate messages received from the RIP from thecommon format into a printer specific machine language; wherein messagesreceived from said plurality of printers announce features and optionsavailable at said plurality of printers to said RIP, wherein said RIP,actively announces the received features and options of said pluralityof printers to said DSF, and wherein the announced features and optionsavailable at said plurality of printers are presented via a userinterface at said DSF; wherein options selected, via said userinterface, at said DSF are sent to a particular printer of saidplurality of printers, via said RIP, along with or subsequent to sendinga print job as printer specific job parameters, wherein said particularprinter is assigned to execute the print job based on the announcedfeatures available at said particular printer, the print job sent in thecommon format; and wherein said particular printer's limitations areknown in advance and only printing options that are available at saidparticular printer can be selected in jobs sent to said particularprinter, via said RIP.
 24. The printing workflow system of claim 23,wherein said printer specific parameters provided subsequent to sendinga print job to said particular printer effect any of updating said printjob while said print job remains at a present state at said particularprinter; and rerouting said print job by removing said print job from acurrent position and resubmitting said print job either with differentparameters or sending said print job to another RIP or printer if acurrent RIP or printer is busy or not available.
 25. A printer adapterfor establishing active monitoring and management functions for aprinter otherwise lacking such active monitoring and managementfunctions, comprising: a receiver for receiving messages ornotifications, in a common format, from registered senders via a rasterimage processor (RIP) comprising a hub for establishing and maintainingcommunication, via a message having the common format, of multiplecombinations of printer specific parameters between any of a digitalstore front and a planning and scheduling system and said printeradapter; an interpreter for interpreting said received messages ornotifications, wherein said received messages and notifications includeprinter specific job parameters sent along with or subsequent to a printjob, said printer specific parameters based on options selected, via auser interface at any of said digital store front and said planning andscheduling system; a translator for translating said messages ornotifications from a communication language in said common format into aprinter machine language; an active handler for modifying a printerdatabase to create an internal event at said printer, and for sendingmessages to a printer UI or connected applications; and a sender foractively sending messages in the common format that announce featuresand options available at said printer to any of said digital store frontand said planning and scheduling system, via said RIP, wherein theannounced options available at said printer are presented via said userinterface, and wherein the announced features are used by said planningand scheduling system to assign said print job to said printer, via saidRIP.
 26. A printing workflow system, comprising: a raster imageprocessor (RIP) comprising a hub for establishing and maintainingcommunication, via a message having a common format, of multiplecombinations of printer specific parameters between any of a digitalstore front (DSF) and a planning and scheduling system, and a pluralityof printers lacking active monitoring and management functions, each ofthe plurality of printers associated with a printer interface comprisinga printer adapter that establishes such active monitoring and managementfunctions, said printer adapter configured to actively send messages tosaid RIP in the common format and translate messages received from theRIP from the common format into a printer specific machine language;wherein messages received from said plurality of printers announcefeatures and options available at said plurality of printers to saidRIP, wherein said RIP, actively announces the received features andoptions of said plurality of printers to said DSF and said planning andscheduling system, and wherein the announced features and optionsavailable at said plurality of printers are presented via a userinterface at said DSF; wherein options selected, via said userinterface, at said DSF are sent by said planning and scheduling systemto a particular printer of said plurality of printers, via said RIP,with a print job as printer specific job parameters, wherein saidparticular printer is assigned by said planning and scheduling system toexecute the print job based on the announced features available at saidparticular printer, the print job sent in the common format; wherein alimitation of said particular printer is known in advance and onlyprinting options that are available at said particular printer can beselected in jobs sent to said particular printer; and a dashboard andnotifications server for interfacing operators and a dashboard userinterface to a dashboard agent which, in turn, is in communication withsaid RIP; said dashboard and notifications server comprising acentralized provider of a dashboard and notifications for all printersassociated with said printing workflow system.
 27. The system of claim26, said dashboard user interface providing any of printer related data,including any of performance, utilization, and statistics; job andconsumable related data, including any of jobs and costing, ink usage,area printed by media type, and jobs printed by media type; jobs; andmaterial costs.